Magnum One/Magnum One (Mid-American Digital) (Disc Manufacturing).iso/d16/wincon.arc/WINCON.TXT

Text File | 1991-08-09 | 29.5 KB | 642 lines

(Steve)[70304,1715] Welcome.  I'm Steve Ballmer, Microsoft's Senior
Vice President of Systems Software.  My purpose here this  afternoon
is to explain our systems strategy, collect feedback, and answer
questions from the development community.

Over 4 million copies of Windows 3.0 have been sold, firmly
establishing it as the graphical operating system standard for
desktop PCs. Developers have purchased 60,000 Windows 3.0 SDKs and
over 1,200 applications are currently shipping from 730 vendors.
The overwhelming success experienced by Windows has sent us a clear
message and we have responded.  We are 100% committed to one
platform: Windows.

Later this year we will release Windows 3.1, a significant improvement
over 3.0 offering increased stability, performance, and added
functionality including TrueType support and application integration.
We will also broaden Windows' appeal with multimedia and pen extenstions.

In 1992 the NT (New Technology) operating mode will be added,
enabling Windows to become the ideal server and high-end desktop
platform.  Windows running in NT mode will support symmetric
multiprocessing, file system fault tolerance, C2-level security, and
full downward compatibility with standard and enhanced mode Windows
applications.

Following the release of Windows NT mode, the Windows 32 technology
will be incorporated into Windows enhanced mode running on DOS.
Enhanced mode will gain preemptive multitasking, multiple threads,
and separate address space for enhanced mode applications.  We will
also continue to refine Windows with additional user interface enhancements
and a more extensible network architecture.

Given this full committment to Windows, you may be wondering about DOS
and OS/2.  DOS will receive additional networking support and reductions
in memory requirements, which will benefit both DOS and Windows applications.
There are clear advantages to running Windows on both the client and server,
so we will offer server applications including LAN Manager for Windows NT
mode.  For those customers who have made prior investments in OS/2
applications, we will provide an OS/2 1.X and 2.0  migration layer in
Windows NT mode.

One final note before I begin addressing your questions.  We recognize
the importance of you, the development community, in the current and
future success of Windows.  We are committed to provide you with a consistent,
scalable systems architecture which fits into one strategy: Windows.

(Mike @ Z-Net PC)[75300,1642]  Mr. Ballmer, now that MS has defined the Windows
API as "the" standard API for graphical development, what will MS do to "make it up"
to the many developers who have invested so much money into the MS...
version of the OS/2 SDK?  Thanks.

(Steve)[70304,1715] Two things:  First, we are building an OS/2 subsystem
for windows NT. This will allow OS/2 applications to run on NT with little
or no modification.  Second:  We are considering upgrading purchasers of the
OS/2 SDK's to windows in a most reasonable fashion. Stay tuned for news.

% Moderator recognizes queue #3
  Marc Perkel <19>

(Marc Perkel)[76505,1120] As a small mom and pop software developer I am
concerned about converting my existing programs to Windows. Now that Novell
has bought DRI and DOS 6 is going to be out next month, and IBMs going to
support it. Why shouldn't I stay with DOS?

(Steve)[70304,1715] IBM has no announced plan to support DR DOS.  Second:
We do expect MS DOS to remain popular for many years to come.  There is none
the less incredible customer demand for graphical applications on Windows.
It is the largest growth applications market, bar none.

% Moderator recognizes queue #4
  Don Stegall <4>

(Don Stegall)[76702,1603] There were a lot of interface changes from 2.x
to 3.0 how much is going to change in the future?

(Steve)[70304,1715] There will be additions to the windows API as we go
forward.  There will not be changes, however, in general.  We will continue
to evolve the user interface consistent with the vision of information at
your fingertips.

% Moderator recognizes queue #5
  Mike Sax <10>

(Mike Sax)[75470,1403] Windows currently lacks a batch language.  Will
you put some kind of Basic into a future release of Windows and provide
an API for it, so applications can use it as a common macro language ?

(Steve)[70304,1715] We will enhance windows OLE to support common macro
languages. We will build a line of these ourselves and include that technology
with windows as requested.

% Moderator recognizes queue #6
  jstern <50>

(jstern)[76200,3614] Hi, I have another API question.  I wonder what the NT
api will look like.  Up to now, to add a GUI to an ap, we've had to manage
memory, fonts, disk i/o, etc. differently as well.  Slows progress.  MS's
VisualBasic and Borlands C++ show better "API"s, but have limitations.  Is
there a model for a new, higherlevel API, perhaps ala XWindows, that we might
see in NT?

(Steve)[70304,1715] Two things:  First, the WIN-32 API in NT is a complete
operating systems API---including kernel networking graphics and user interface
services.  Second:  We are building an applications framework for windows
applications with appropriate language support to make building new windows
applications easier.

% Moderator recognizes queue #7
  David <59>

(David)[73040,334] NT is slated to support C2 security.  Will this be
implemented so that a user may choose to use security features only if
they need them?  Some current Windows apps require "knowledge" of other apps
that might be prohibited with C2 security.

(Steve)[70304,1715] C2 security is discretionary.  B level security is
mandatory.  All Win 32 applications live in separate address spaces but there
are APIs to help applications that depend on living in the same address
space today.

% Moderator recognizes queue #8
  Dan Higdon <53>

(Dan Higdon)[70303,1526] Ok, two things..First, what level of support will you
keep for 286 processors? ..Also, will the application frameworks that you
mentioned above be made available through your open tools policy?  Thanks.

(Steve)[70304,1715] We will continue to support 286 through Windows' standard
mode but some new features will be 386 only.  Yes, the application framework
will be made available to developers.

(Dan Higdon)[70303,1526] Sorry, one more thing  Will WIN3.1 Standard mode
support the "no bios" disk driver for protected mode?

(Steve)[70304,1715] The no-bios disk driver is what we call "fastdisk" and it
depends on the .vxd driver model which is 386-only therefore in enhanced mode.

% Moderator recognizes queue #9
  Paul Grous <32>

(Paul Grous)[75300,1247] I would like to know if Steve is using a
Windows-based terminal program at this moment to access compuserve?

(Steve)[70304,1715] Yes.  Dynacomm.

% Moderator recognizes queue #10
  Mike Komar <29>

(Mike Komar)[76702,1207] What further dev. in terms of MS-DDK can we
expect to see in the future? (example TIGA, S3, Realized Bitmap?)

(Steve)[70304,1715] 3.1 includes enhancements to allow devices like
TIGA to perform better where their bitmap lives on the graphics adapter.

% Moderator recognizes queue #11
  Marcellus Buchheit <28>

(Marcellus Buchheit)[100020,1723] Ok.  How difficult is the hardware access
under NT?  Is it possible to address a slot extension further with port
accesss or need I for this a device driver?

(Steve)[70304,1715]  Direct hardware access under NT requires a device
driver.

% Moderator recognizes queue #12
  Brent Hughes <80>
((Brent Hughes)[70700,460] Any comments about the death of MDI?

(Steve)[70304,1715] MDI is alive and well, we are always considering
improvements to our user interface guidelines.  Please send us your
suggestions.

% Moderator recognizes queue #13
  Jim Palmer <26>

(Jim Palmer)[70650,476] Could you talk about Windows and multiple hardware
platforms?

(Steve)[70304,1715] Windows NT is a portable system.  We are currently
running it on Intel and MIPS systems.  We will consider other ports in
the future.

% Moderator recognizes queue #14
  Legare Coleman <73>

(Legare Coleman)[76247,3673] OK - MS's own apps are currently one of
the biggest roadblocks to getting WIN in my company.  What is MS doing
to make it's own app compatible.  For example W4W, MAC WORD and DOS WORD
all able to use same document file?

(Steve)[70304,1715] They can all read and write each others' files but
we are always working to acheive even higher levels of compatibility.

% Moderator recognizes queue #15
  Mike Sax <10>

(Mike Sax)[75470,1403] Ok.  When are you going to add a drag & drop interface
to Windows and are you going to provide an API for communication betweens
DOS programs (in enhanced mode) and Windows programs ?

(Steve)[70304,1715] First, 3.1.  Second, DOS applications can talk to
Windows applications via TSRs or VXDs in enhanced mode.

% Moderator recognizes queue #16
  Dan Higdon <53>

(Dan Higdon)[70303,1526] Since Windows NT is part of ACE.   What level of
interoperability can we expect Between NT and SCO Unix, in terms of data
and source code compatability?

(Steve)[70304,1715] None.  SCO UNIX and Windows NT are completely
independent parts of ACE.  We do provide a version of LAN Manager for SCO
UNIX through SCO.

% Moderator recognizes queue #18
  Wayne Erfling <57>
((Wayne Erfling)[71370,3644] From my perspective, the common user interface
Windows offers gives authors an opportunity to write "multiple application"
utilities.  Among those I have purchased is one that allows me to customize
cursors, and another lets me use the middle and right mouse buttons.  My first
utility "dips into" application menu bars to add new functions and enhance
user productivity. My question is:  Is this type of "multiple application"
utility a recognized category of program?  Or could we experience problems
when we "dip into" applications, for example from a DLL?

(Steve)[70304,1715] No.  We think these types of applications are great and
think that OLE will encourage the creation of even more of these types of...
utilities.


% Moderator recognizes queue #20
  Don Stegall <4>

(Don Stegall)[76702,1603] Steve, I asked my question improperly the first
timeThere were a lot of user interface changes from 2.x to 3.0 title bar
and scroll bar bitmaps, etc.  How much is the user interface going to change
over the long haul?  3D title bars and sizing borders for instance.

(Steve)[70304,1715] Sorry I misunderstood your first question. 3.1 will have
little or no change in user interface appearance.  But there were proposals
to do more.  You can expect more in some future release.

% Moderator recognizes queue #21
  Marc Perkel <19>

(Marc Perkel)[76505,1120] I've read a few articles about MS DOS 6, can you
tell us what features it will have, how it will compate to DR DOS 6, and
how it fits.into the NT picture, and when you think it will (DOS) be obsolete?

(Steve)[70304,1715] Future versions of DOS will continue for many years
to come.  Focus of the next releases will be in two areas.  1) There are
still many utility enhancements and improvements people would like to see
in DOS.  2) To enrich MS-DOS as an operating system, and to give customers more
memory, better multitasking, and better networking.  We will migrate some
additional OS technology from Windows back into DOS.  Candidates might include
multiple DOS application support, support for VXDs, etc.

% Moderator recognizes queue #22
  Martin Hill <49>

(Martin Hill)[70314,313] OK  Is help on the way for developers who need to
offer their Win Apps in Int'l markets (Japan and Greece in particular)? Will
Unicode play a role? If so, when?

(Steve)[70304,1715] We currently offer a version of Windows for Japan, Korea,
and China.  Win 32 applications will be able to support Unicode, which will
make life simpler.  I do not know our current plans for Greece, sorry.

% Moderator recognizes queue #23
  Dave Rogers <23>

(Dave Rogers)[76366,2171] I work for a company that made an OS/2 2.0
directional decision several months ago, based on the then-current joint IBM
and Microsoft operating systems "responsibility" plans.  Now that world has
turned upside-down, and you are in direct competition with IBM et al for the
hearts and minds of corporate america, why should we believe that you can smother
the gorilla?  Why shouldn't developers expect a rapidly growing demand for OS/2
applications from corporate America?

(Steve)[70304,1715] We are not trying to smother the gorilla.  We are trying
to and will sell many millions of copies of Windows over the next years.
We expect close to 8 million new Windows users in the next year alone.
IBM has recognized the importance of Windows, hence their goal of 'better
Windows than Windows' support.  Writing Windows applications looks like a safe
bet for developers.

% Moderator recognizes queue #24
  david freitag <82>
((david freitag)[70541,1374] Will the next release of Windows support drag
and drop features, support high resolution graphics, allow for use of a
mouse in a Dos window and use 32 bit capabilities? When is the next version
scheduled to be released?  Also, does the Apple lawsuit inhibit you by forcing
you to stay 'safe'?.

(Steve)[70304,1715] 3.1 will be released the end of this year.  It has
drag & drop, support for high resolution graphics and 32 bit capabilities
like device drivers and paging.  We do not currently plan to support the use
of a mouse in a DOS window.  Generally, this will cause two mouse cursors to
appear, based upon the way most DOS applications draw the mouse cursor.  The
Apple lawsuit does not force us to 'stay safe'.  We have not and will not violate
Apple's copyrights, but we will not allow the lawsuit to intimidate us.

% Moderator recognizes queue #26
  Mike Gilpin <62>

(Mike Gilpin)[70640,462] ok What is the status of WLO as far as Microsoft's
commitment to make it work with applications that need to be ported to OS/2.
We would love to live in a simple world with only Windows, but competitive
reasons require us to have OS/2 version.  To commit to the WLO approach only
makes sense if Microsoft are committing resources to ensure its completeness
and correctness, as those doing ports discover problems. To what extent
can we expect WLO to be supported in this way?

(Steve)[70304,1715] We will support developers who choose to use WLO to
target OS/2.

% Moderator recognizes queue #27
  Kenn Wynn <44>

(Kenn Wynn)[76307,1646] ok. Can we expect thermal color printer soupport in Win
3.1 and can you talk about the Solution Series appletts?

(Steve)[70304,1715] There are printer vendors doing Windows drivers for their
color printers.  I'm not sure what the 'Solution Series' is -- unnanounced
Microsoft app?

% Moderator recognizes queue #30
  David <59>

(David)[73040,334] Will Windows 3.1 be marketed in such a way (price, etc.)
that you expect MOST users to upgrade quickly?  I am concerned about marketing
a product that REQUIRED 3.1 features.  What is the MS philosophy as to backwards...
compatibility to 3.0

(Steve)[70304,1715] There will be an attractive upgrade from 3.0 to 3.1 and we
encourage you to require 3.1 features if that makes sense for your app.  3.1
will be upward compatible with 3.0, currently we have only a few compatibility
problems in our bug database.

% Moderator recognizes queue #33
  Greg Carter <84>

(Greg Carter)[72050,2754] Is MS planning on producing "Visual - C? GA

(Steve)[70304,1715] We will have a Windows hosted C environment very soon.

% Moderator recognizes queue #34
  Ted <6>

(Ted)[76703,4343] ok  You've stated that there have been 4 million copies of
Windows sold, and that you expect 8 million *new* users of Windows in the next
year. What I'd like to know is how many of those people are actually *using*
Windows and Windows applications? I know of quite a few people who either
purchased Windows, or had it "bundled" with their computer, yet they haven't
touched it.  Aren't these figures misleading?

(Steve)[70304,1715] We recently completed a market research study where we
called at random 11,000 US phone numbers and found 216 people who owned
Windows.  80+ percent of those people say they use Windows.  60+ percent of
those people say they own 1 or more Windows application.  That counts retail
and OEM copies of Windows.and is our best data.   Also, SPA reports that sales
of Windows applications in May were 40% the dollar volume of MS-DOS applications
I don't think the figures are misleading.

% Moderator recognizes queue #35
  Lyle Groome <34>

(Lyle Groome)[75136,1033] Could you address the future of OLE and also future
extensions to allow OLE / DDE to operate across a network.  Also your current
plans for support of "Objects", i.e. OOFS, better Windows support of C++, etc.

(Steve)[70304,1715] We are currently working on the OLE 2 protocol
specification.  The focus is on "in-situ editing" and on encapsulating
applications commands as OLE objects.   We are in general working to extend
OLE and DDE accross the network and provide file system support for tracking
OLE objects.   We will bring out Windows class libraries for C++ in addition.

% Moderator recognizes queue #36
  Mike Kogan <68>

(Mike Kogan)[76711,212] Will the Windows NT OS/2 subsystem provide BINARY
compatibility for 16-bit and 32-bit OS/2 apps off the shelf?

(Steve)[70304,1715] Good to hear from you Mike.  Been a long time  The
OS/2 subsystem for Windows NT will run OS/2 1.X and 2.0 applications with
little or no modification.  The entire subsystem will not be complete until
1993, but we should have complete support for non-PM applications in '92.
In fact, we already have some OS/2 server applications up and running on the
OS/2 subsystem.

(Mike Kogan)[76711,212] Does little or no modification mean yes or no?

(Steve)[70304,1715] Yes for some applications, and no for others.

% Moderator recognizes queue #37
  Chiaki Kato <41>

(Chiaki Kato)[70721,1620] Two questions. How much you expecting the cost
for updating and reatil 3.0 to 3.1 and NT.  2) Does 3.0 App. 100% work on NT?

(Steve)[70304,1715] The 3.0 to 3.1 upgrade will be reasonably cheap.  We
have not picked a price for NT, but it is targeted at higher end systems.
3.0 applications will run on NT.  The only restriction is that NT will not run
DOS device drivers or today's Windows enhanced mode VXDs.

% Moderator recognizes queue #38
  Brent Hughes <80>

(Brent Hughes)[70700,460] I read an article by Charles Petzold with some
general comments about Windows versus Presentation Manager.  He much preferred
PM.  He felt it a pain to have to go back and update his famous book on programming
windows to upgrade it to Windows 3.0.  Do you recall the article?  Will future
versions of Windows make Charles happy?<g>

(Steve)[70304,1715] We will continue to enhance Windows which will please
Charles.  However, we will not change the existing Windows programming model
to make it aesthetically better.  We tried that once with PM.  Compatibility
is the important thing.

% Moderator recognizes queue #39
  Runnoe (FSE) <46>

(Runnoe (FSE))[76701,144] First, I have read in the trade press that you
do not think IBM will be able to deliver the next major OS/2 upgrade by the
end of the year. Is that an accurate reflection of your views? Second, virtually
all of my company's products are Windows apps. We do have an OS/2 product,
developed back when MS was still recommending it. Does Microsoft now recommend
developers drop all OS/2 development and concentrate on Windows?

(Steve)[70304,1715] I think IBM will have a tough time delivering an OS/2
product that delivers 'better Windows than Windows' anytime.  I do recommend
focusing your development on Windows.   At Microsoft our development targets
Windows with the exception of existing applications and server applications
which target OS/2 and Windows NT.

% Moderator recognizes queue #41
  Dan Higdon <53>

(Dan Higdon)[70303,1526] Ok  Why did you drop support in Win3.0 for windowing well
behaved" dos apps?  In particular, development tools and command.com?  (I mean in
Standard mode, of course.) Do you plan to allow "benign" programs like compilers
and linkers to run in graphics windows ever?

(Steve)[70304,1715] I do not remember why this is not in 3.0.  We provide this
support in 3.1 absolutely.

% Moderator recognizes queue #42
  Omar Loggiodice <7>

(Omar Loggiodice)[74040,1543] Steve, when is MS going to improve windows' direct
hardware interface providing I/O ports or dynamic DMA access (without memory
fragmentation!)? Thanks.  Another question, when will you provide class libraries
for Windows? Thanks again.

(Steve)[70304,1715] Class libraries will come this year.  Can you amplify on your
first question?  I'm not sure what you want to know.

(Omar Loggiodice)[74040,1543] I want to know if windows will provide a
consistent interface for hardware controlling (such as hardware that uses DMA)

(Steve)[70304,1715] I'm afraid I do not know the answer.  VXDs do provide great
hardware access, but I will ask Alistair Banks to respond to your question later.

% Moderator recognizes queue #44
  Jim Gwaltney <3>

(Jim Gwaltney)[70253,2561]  Pardon my ignorance, but is a "VXD" a virtual Dos
machine or what?

(Steve)[70304,1715] VXD refers to the Windows 32 bit protect mode device
driver interface supported in Windows 3.0 and 3.1.  The name "VXD" is misleading
but the technology does come from our work supporting virtual DOS machines.

% Moderator recognizes queue #47
  DBROCK <69>
((DBROCK)[70673,3107] ok  How will 3.1 support network users logging into
different HW configs who want their "Personal" defaults such as color schemes,
program groups, etc? In other, will I be able to setup a "local" windows diectory
with the specific HW info and drivers and a "Network" directory with the user's
"Personal" config files such as progman.ini, control.ini, etc?  Also, is there
a separated product "Network Extensions"? What does NT signify? THANKS!!

(Steve)[70304,1715] 3.1 provides a nice set of improvements in this area.
Although we still know that there is great room for improvement.  There
is no network extension product.  NT stands for "New Technology" and Windows
NT will run LAN Manager.

% Moderator recognizes queue #48
  Michael R. Sengstoc <12>

(Michael R. Sengstoc)[76216,3324]  On our 300+ node Novell 3.11 token ring
network, we have 50 or so "windows users", after loading all required token
ring device driver (LAN support drivers, etc..) and loading network shells,
you come up with a very unstable network environment that has to be fine tuned
on a user specific level still producing quirky UAEs at random is there any hope
of relief from such problems in 3.1 or is there any specific documents or
specifications that MS has published that would help in this type of problem.

(Steve)[70304,1715] Windows 3.1 has put an emphasis on better network
compatibility and greater robustness.  We have worked closely with Novell
on compatibility with Netware.  I do encourage you to download our Dr. Watson
utility located in Library 16 of the MSOPSYS forum.  It will allow you to give
us valuable data on where you problems are occuring so that we can make sure
they are resolved.

% Moderator recognizes queue #49
  Alan Hill <74>

(Alan Hill)[76067,2070] What's MS position on OS/2 2.0 support?
Specifically, Will MS provide Lan Manager code to enable an OS/2 2.0 workstation
to be a full client (re-directed I/O and IPC) to Lan Manager servers running over
OS/2 1.3

(Steve)[70304,1715] Yes.  LAN Manager will support OS/2 2.0 clients and in
fact LAN Manager will also support OS/2 2 on the server as it stabilizes.
Hope things are good in Cincinatti, Alan.

% Moderator recognizes queue #50
  Ken Bannister <20>

(Ken Bannister)[70314,242] ok  We develop without the SDK, but cannot
purchase the Adv. Interface Design Guide separately.  Any plans to change
this policy?

(Steve)[70304,1715] Please send your address to Alistair Banks 73740,3417
and we will send you one.  Good suggestion that we make this available separately.
Thanks.

% Moderator recognizes queue #51
  Marcellus Buchheit <28>

(Marcellus Buchheit)[100020,1723] Ok, two questions  1. What is the future
of VxD? You said, that VxD doesn't run under NT.  Is this only a binary level
problem or a new driver philosphy problem?  2. Is NT a real time kernel? For
example, it is possible to display a message box as a reaction of a hardware
interrupt? This would be very needed to use windows in a technical process
environment.

(Steve)[70304,1715] VXDs will be supported on DOS into the future.  NT
has additional device driver services and requirements since NT supports
multiprocessor machines.  Second, I do think NT will allow real-time response
to interrupts although that is not its primary design goal.

% Moderator recognizes queue #52
  Legare Coleman <73>

(Legare Coleman)[76247,3673] OK - In your discussion of DOS 6.0, you didn't
mention the file system.  Any plans to fix that to do things like identify the
file creator, have a Resource fork, etc.  All of which Windows desparately needs.

(Steve)[70304,1715] There will be evolution in the file systems.  This work
may well be pioneered in Windows and driven by the advanced link tracking
and content indexing work we want to do there.

% Moderator recognizes queue #53
  Roland Waggoner <40>

(Roland Waggoner)[76625,2440] Will ther be an inexpensive upgrade for the
3.1 SDK? Will the Windows C environment you mentioned earlier support 32
bit code?

(Steve)[70304,1715] Yes to both.  To clarify, we will provide 32 bit code
in C this year although maybe not from a Windows hosted environment at first.
Windows applications on DOS will run on NT.

% Moderator recognizes queue #54
  Dan Mabbutt <45>

(Dan Mabbutt)[72717,2461] ok  Can you tell us what features windows will
have for the IBM corporate shop?  In particular, in a client server environment
for an IBM SNA host over a Novell network.  What support will MS offer the
corporate developer.  Also if IBM has a "blue ninja"  are you a ninja too and
what color are you?

(Steve)[70304,1715] Windows has excellent connectivity to IBM host systems.
APPC, DB2 gateway support, AS/400, AS/400 database access, and a boatload
of 3270 emulators.  All of this support is or will be made available on
Novell networks.  I am not a Ninja, I am a guy trying to improve Windows.
Does the world need A Better Ninja than Ninja?

% Moderator recognizes queue #55
  John Ceneviva <65>
((John Ceneviva)[76477,3044] Thanks, I believe that the difference between
OS/2 2.0 and Win 32 are purely cosmetic and political.  Both are / will be
capable of preemptive multitasking, LAN-able from within the environment, etc
Is the only difference then the name on the outside of the box?

(Steve)[70304,1715] No, the differences are more than cosmetic and political.
Windows is compatible with the large and increasing number of Windows
applications.  Also, our strategy for Windows is scalable, starting with
standard mode for 286 systems, enhanced mode for 386 desktops and NT mode
for x86 and RISC workstations and all servers.  I think this scalability and
compatibility are key features of Windows.   Also, Windows is being extended
with pen, multimedia, distributed and object oriented extensions.  I do not
know the plans for these capabilities in OS/2.  They may only come in operating
systems like Go, OSF/DCE, and Pink Patriot, which are not OS/2.

% Moderator recognizes queue #58
  Robert Hunley <75>
((Robert Hunley)[76506,401] ok I have two questions I would like to know the
differences of  Windows 3.1, NT, and Win 32, And how they relate to one another.
Can I post exerpts or the transscript of this Conference on a local BBS?

(Steve)[70304,1715] Yes, you can post excerpts of this conference.  Windows
is an operating system with three modes; standard, enhanced and NT.  Standard
and enhanced come in 3.1, and run on DOS.  NT comes in a separate box called
"Windows  NT."  Windows 32 is a programming interface which will be supported
in NT mode and enhanced mode.  I hope that helps.

% Moderator recognizes queue #60
  Steve Buck <71>

(Steve Buck)[72411,3264] Thanks,  Two questions. 1) are there any plans
to add dynamic linking capability to DOS for non-Windows apps? 2) are there
any plans to host the Windows API on X/Motif?

(Steve)[70304,1715] 1) It is certainly a possibility.  2) There are no plans
to host the Windows API on X/Motif.  People have done X clients and X servers
for Windows.

% Moderator recognizes queue #62
  Don Stegall <4>

(Don Stegall)[76702,1603]  Are 3.0 display and printer drivers going to have
to be updated for 3.1  For some compatibility or total compat ???

(Steve)[70304,1715] No.  They will not.  To take full advantage of TrueType,
we are updating the Windows printer drivers in the Windows box, but all 3.0
printer drivers continue to work.

(Don Stegall)[76702,1603] What about displays

(Steve)[70304,1715] Displays do not require modification for 3.1. Thanks to
all of you for your time today.

% The conference has ended
  Thank you for attending